Docs: Convert document Overviews and Best Practices to markdown #4512
Conversation
| Toggle/ @phkuo | ||
| Tooltip/ @micahgodbolt | ||
|
|
||
| ## Docs |
There was a problem hiding this comment.
I think it makes sense to use the same code owners as the rest of the component for now, but over time we'll want to find design owners who can review the usage guidelines.
|
Approved with the note that this is just a move. It is hard to read through all comments. Are there any changes that are not just a physical move? |
|
@manishgarg1 The only changes other than converting to markdown:
|
|
Overhauled the "Themes" page so I could use markdown. It now pulls the theme palettes dynamically instead of being hardcoded. Added semanticColors as well. |
|
@jordandrako does it leave out the deprecated semantic slots? |
|
@phkuo Finished adding |
|
Sorry for the delay @jordandrako. This is an awesome set of changes. Looking now. |




Pull request checklist
$ npm run changeDescription of changes
For all components (excluding those in Experiments package)
componentUrls to component example pagesAlso changed/updated/fixed:
ComponentPagepattern like all the other components. This enabled me to use markdown for the description.palettevaluespaletteandsemanticColorsvalues usinggetTheme(true)insteadtheme.ts_makeSemanticColorsFromPalettethat returned empty strings for deprecrated semanticColors.getTheme,loadTheme, andcreateThemefunctions to return/* @deprecated */on deprecated semanticColors. This is mainly for documentation that calls the function (like the rewritten ThemePage). It's opt-in so it doesn't break existing parsers.Let me know if the bugfix and opt-in, or any other added changes should be in separate PRs.
Focus areas to test
Test if edit button link will go to the right place.